Thanks for the contribution!
But this repo's idea has a bigger issue in general - it's simply not possible to export a mount from the container. I realized that after i made a release :). Just curious how useful this docker image is for you?

Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion.

Dockerfile, line 9 [r1] (raw file):
i'd use at least a package installed directly from some commit/feature branch, instead of keeping the patch directly in this repo

Comments from the review on Reviewable.io

Regarding the patch, it would be ideal, unfortunately it's pending as a comment right now, thus the patch seemed like the easy way to go about it.

I'll have to do some testing, but I'm unsure what the issue is? Shouldn't a mount be a simple drive/folder endpoint and thus you can export it using the regular VOLUME and VOLUME_FROM - I can deploy my patch and see what it looks like?

this image DOES mount the s3 folder fine, that's not the concern, but there's no way you can use that mount from other containers, as volume_from would use just an fs folder from container, and NOT the s3 folder contents.
You can check that yourself.

I see - I missed that part. This current patch seems to break anyway, as I get the dreaded SSL: CERTIFICATE_VERIFY_FAILED that some aws-cli users have reported.